Confidence Score: 5/5

Safe to merge — all changes are scoped to test infrastructure and dev-time package resolution, with no impact on published output.

The publishConfig.exports override correctly preserves the compiled dist/ paths for consumers of the published package, and the files field already limits publish artifacts to dist/. The new require-cache.ts ESM entry is an exact copy of the existing .cts file, satisfying the updated import condition used only in the local dev environment where jiti handles execution. Test-side changes are minimal and well-scoped.

No files require special attention.

_{Reviews (5): Last reviewed commit: "use source files instead of dist files i..." | Re-trigger Greptile}

Walkthrough

The pull request modifies the @tailwindcss-node package exports configuration to reference TypeScript source files instead of built distribution files. A publishConfig section with public access was added to expose dist artifacts during publishing. A clearRequireCache function was added to provide functionality for deleting entries from Node's require cache. Tests in @tailwindcss-postcss and tailwindcss packages were updated to include console.warn spies and verify warning outputs via inline snapshots and assertions.

_{Comment @coderabbitai help to get the list of available commands and usage tips.}